Method and system for detecting malware

ABSTRACT

A system and method of analysis. NX domain names are collected from an asset in a real network. The NX domain names are domain names that are not registered. The real network NX domain names are utilized to create testing vectors. The testing vectors are classified as benign vectors or malicious vectors based on training vectors. The asset is then classified as infected if the NX testing vector created from the real network NX domain names is classified as a malicious vector.

CROSS-REFERENCED TO RELATED APPLICATIONS

This application claims benefit of U.S. Provisional Patent ApplicationNo. 61/292,592, filed Jan. 6, 2010, and U.S. Provisional PatentApplication No. 61/295,060, filed Jan. 14, 2010, the contents of whichare incorporated herein by reference in their entireties.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 illustrates a system for detecting malware, according to oneembodiment.

FIGS. 2-4 illustrate a method for detecting malware, according to oneembodiment.

FIG. 5 illustrates various elements involved in domain name resolution.

FIGS. 6-10 illustrate examples for detecting malware, according toseveral embodiments.

DESCRIPTION OF EMBODIMENTS OF THE INVENTION

FIG. 1 illustrates a system for detecting malware, according to oneembodiment. FIG. 1 illustrates at least one network 101 (e.g., theInternet) connecting at least one NX application 105 (described below)on at least one server 120 to at least one honeypot 110 and at least oneentity's network 125 (e.g., a private network of a company). The NXapplication 105 can determine if one or more assets 115 (e.g.,computers) on the at least one entity's network 125 is infected withmalware. It should be noted that the asset can be a simple asset (e.g.,mainframe hardware, storage) or a complex asset (e.g., licensedsoftware).

The determination of whether an asset is infected can comprise:collecting NX domain names from at least one honeypot and at least oneasset; using the honeypot NX domain names to create training vectors;using the real network NX domain names to create testing vectors;classifying the testing vectors as benign vectors or malicious vectors;and classifying the at least one asset in the at least one real networkas infected if the NX testing vector created from the real network NXdomain names is classified as a malicious vector. (It should be notedthat the testing vectors can be classified using: simple internal assetsinfected with known malware; simple internal assets infected withunknown malware; or complex internal network assets; or any combinationthereof.)

NX domain name information is useful because some malware takesadvantage of existing domain name system (DNS) services such as freedomain testing (e.g., determining whether a new domain name isavailable). Such malware can use a domain name generator that employs aseed, such as the date, together with an algorithm to generate a set ofdomain names. The command and control (C&C) can try to register thegenerated domain names until a registrable subset of domain names hasbeen identified. An infected computer can then use those daily-generatedset of domain names in order to establish a new communication channelwith the C&C. The victim computers will employ the same seed (i.e. date)and algorithm to generate the same set of domain names. The victimcomputers will then use the generated domain names in attempts tocontact the C&C computer. Eventually, each victim computer will find adomain name that was registered for the C&C computer to enable dailycommunication between the C&C computer and the victim computers. Bychanging the domain name for the C&C computer (e.g., daily), it becomesdifficult to statically black list the domain names or the IP addressesof the C&C computer(s).

Thus, malware which uses the above domain name resolution to establishcommunication with a C&C can produce many NX-Domains (NXs), which can bedomain names that have not been registered with an authoritative DNS andcan be observable at a recursive DNS server (“RDNS”). RDNS servers mapdomain names to IP addresses, also called “resolving DNS queries”. Ifsuch a mapping between a domain name and an IP address doesn't exist,the RNDS can send back to the initiator of the DNS query a“Non-Existence” response. The Non-Existence response can indicate thatthe domain name does not have an IP address, and is thus an NX-Domain(NX). Monitoring the NXs observable at a RDNS can provide the ability tocollect all possible NXs generated from all computers connected to theRDNS.

FIG. 2 illustrates a method for creating training vectors, according toone embodiment. Referring to FIG. 2, in 205, malware NXs can becollected from at least one honeypot (e.g., an Internet-attached serverthat acts as a decoy, luring in potential hackers in order to studytheir activities and monitor how they are able to break into a system)by an NX application 105 and grouped into sets of, for example, 10.

The malware NXs can be collected so that a classifier can be trained ina controlled environment to recognize different categories of infectedcomputers. For example, FIG. 5 illustrates a honeypot networkconfiguration. In this example, the virtual machine names “kritis”operates as an internal virtual gateway for the virtual machines dns01,dns02 and dns03, which are infected with malware (e.g., sinowal worm,bobax worm). By monitoring the DNS traffic that originates from infectedvirtual machines dns01, dns02, and dns03, a pure seed of malware domainnames can be obtained.

In FIG. 5, the computer called “minoas” can act as an open recursive DNS((ORDNS), which can be a rDNS server willing to resolve a domain namefor any host in the Internet—inside or outside its network) and as anauthoritative DNS server for root DNS servers. By doing this, the minoascomputer can provide NXs that appear to originate from the root DNSservers. This can force the malware to lookup the next domain name andnot stop probing since the minoas computer does not allow the malware tocontact the root servers. As indicated earlier, the malware needs tomake contact with the C&C at least one time during a set period (e.g.,daily). Thus, by providing NX answers to any domain name that themalware requests, the “minoas” computer can cause the malware to keeplooking up all the generated domain names (e.g., 10,000) because nosuccessful C&C connection will take place. In this way, all 10,000domain names can be observed and can be used to train a statisticalclass that can identify malware based only on this traffic.

Referring again to FIG. 5, the “kritis” computer can be configured togive free Internet access to the dns01, dns02, and dns03 computers forone hour, and for the next eight hours to redirect the DNS traffic tothe “minoas” computer. A simple IP table firewall “rotating rule” at thegateway point (e.g., at the “kritis” computer) can be used to do this.

The VMNET34 computer in FIG. 5 can be a virtual network connectionbetween the virtual machines dns01, dns02, and dns03, and the virtualgateway “kritis”.

Referring back to FIG. 2, in 210, training vectors can be created bytaking each set of, for example, 10 domain names and computing variousstatistical values and putting the various statistical values in avector. Example statistics are illustrated in FIG. 6, which is describedin more detail below.

Those of ordinary skill in the art will see that training vectors can becreated in many other ways, in addition to collecting NXs fromhoneypots, as described above.

FIG. 3 illustrates a method for creating testing vectors, according toone embodiment. In 305, NXs are collected from a real network. In 310,the NXs from the real network can be used to create testing vectors bytaking each set of, for example, 10 NX domain names and computingvarious statistical values and putting the various statistical values ina vector. (It should be noted that both the honeypot NXs and the realnetwork NXs can be grouped in any number, and any algorithm can be usedto group the sets.) It is not known if the testing NXs are malware ornot. Thus, in 315, the testing vectors can be classified as benignvectors or malicious vectors by comparing testing vectors to trainingvectors. A classifier can use the knowledge obtained from thestatistical information from the training vectors and compare it to thestatistical information from the testing vectors to identify eachdifferent malware family in the testing NX vectors. FIG. 8 illustratesseveral types of classifiers that can be used to compare the vectorinformation and identify different malware families. In particular, FIG.8 illustrates the following classifiers: Naïve Bayes, LAD Tree,Multi-Layer Perception, Logistic Regression, and IBK Lazy. Those ofordinary skill in the art will see that many other types of classifierscan also be used. In addition, as explained in more detail below withrespect to FIG. 8, a meta-classifier can use many different types ofclassifiers. In some embodiments, as also described in more detail belowwith respect to FIG. 8, a confidence score can also be given for eachclassifier, as well as for the meta-classifier.

For example, an absolute timing sequence, which can list the domainnames in the order that they are received, can be used to group togetheran example set of ten NX domain names (e.g., from a real network):

fpemcjfbv.com odkigktjzv.biz odkigktjzv.biz.ebay.coml-sjn-sevans.ca1.paypal.com xvoal.com ymtaiwwprpq.bizymtaiwwprpq.biz.ebay.com bcbkdfkg.net bcbkdfkg.net.ebay.comokxixsulas.net

An example of various statistical values that can be computed for theset of NX domain names is illustrated in FIG. 6. Note that many othertypes of statistical values can be computed, and that the vector canhave more or less statistical values than that called for in FIG. 6(e.g., 17). Thus, for the example of 10 NX domain names provided above,the following statistical values can be computed. It should be notedthat some or all of these statistical values can be computed. Inaddition, other statistical values can be computed and used.

-   -   The average of domain name length (not including “.”) (e.g., the        domain name length of the first domain name is 13).        [Value≈12.8333]    -   The standard deviation of the domain name length. [Value≈1.9507]    -   The number of different Top Level Domains (TLDs). [Value≈3.0]    -   The length of the longest domain name (excluding the TLD).        [Value 24.0]    -   The median of the frequency of each unique character across the        entire set of domain names (e.g., the frequency of “o” across        the entire set of 10 domain names above is 10). [Value≈2.0]    -   The average frequency of each unique character across the entire        set of domain names. [Value≈2.2083]    -   The standard deviation of the frequency of each unique character        across the entire set of domain names. [Value≈0.9565]    -   The median of the frequency of each unique 2-gram across the        entire set of 10 domain names (e.g., the frequency of “fp”        across the entire set of 10 domain names above is 1) (Note that        if there is a “.” (e.g., “v.c”) between two characters, the        frequency is counted as 0.) [Value≈0.9565]    -   The average of the frequency of each unique 2-gram across the        entire set of 10 domain names. [Value≈1.0]    -   The standard deviation of the frequency of each unique 2-gram        across the entire set of 10 domain names. [Value≈1.0]    -   The frequency of .com TLDs over the frequency of the other of        TLDs. [Value≈1.5]    -   The median of the frequency of each unique 3-gram across the        entire set of 10 domain names. [Value≈0.3333]    -   The average of the frequency of each unique 3-gram across the        entire set of 10 domain names. [Value≈1.0]    -   The standard deviation of the frequency of each unique 3-gram        across the entire set of 10 domain names. [Value≈1.0]    -   The median count of unique TLDs (excluding .com). [Value≈2.0]    -   The average count of unique TLDs (excluding .com). [Value≈2.0]    -   The standard deviation for the different frequencies for each        different TLD in the set of domain names. [Value≈2.0]

The various statistical values for each set of 10 domain names from thereal network NXs can be put in a vector. An example illustrating thedomain names being transformed to statistical vectors, using thestatistical values set forth in FIG. 6, is illustrated in FIG. 7.Referring to FIG. 7, in 705, the 10 domain names used to create thevector are listed. Note that all of these domain names can come from oneparticular asset 115 (e.g., an infected computer) in the real network125:

fpemcjfbv.com odkigktjzv.biz odkigktjzv.biz.inter1.coml-sjn-sevans.ca1.intern2.com xvoal.com ymtaiwwprpq.bizymtaiwwprpq.biz.inter1.com bcbkdfkg.net bcbkdfkg.net.inter1.comokxixsulas.net

The 17 statistical values corresponding to the statistical values foundin FIG. 6 are illustrated in the vector 710: [12.8333, 1.9507, 3.0,24.0, 2.0, 2.2083, 0.9565, 0.9565, 1.0, 1.0, 1.5, 0.3333, 1.0, 1.0, 0.0,2.0, 2.0, 2.0].

The NX application 105 can then utilize a meta-classifier to classifythe testing vectors. The meta-classifier is a hybrid classifier and cancomprise several generic classifiers. The various generic classifierscan be used (e.g., in parallel) to capture various different statisticalproperties which can potentially lower false positives (FP) and increasetrue positives (TP).

For example, FIG. 8 illustrates a meta-classifier that is comprised offive different classifiers: the Naïve Bayes classifier 805, the LAD Treeclassifier 810, the Multi-Layer Perception Neural Network classifier815, the Logistic Regression classifier 820, and the IBK Lazy Classifier825. The maximum probability includes the classification (given by aparticular classifier for the malware) and the probability of thisclassification being correct. Thus, for example, five different types ofclassifiers can be used to classify the malware as follows:

Classifier 1 (Naive Bayes Meta.) is: notknown (Confidence: 1) Classifier2 (Multi Layer Per. Meta.) is: conficker-B (Confidence: 0.985572986223)Classifier 3 (Logistic Regression Meta.) is: conficker-B (Confidence:0.374297598072) Classifier 4 (LADtree Meta.) is: conficker-B(Confidence: 0.220571723953) Classifier 5 (Lazy IB1 Meta.) is:conficker-B (Confidence: 1)

The majority voting can take the many classifications and determinewhich classification the majority of classifiers found. Thus, for theexample above, conticker-B was the classification the majority ofclassifiers classified the malware as. The final class is the finalclassification based on the majority voting, which is conficker-B.

It should be noted that the meta-classifier can use any number and anytype of known or unknown classifier, including, but not limited to, theabove classifiers. The Naïve Bayes classifier can use estimator classes.Numeric estimator precision values can be chosen based on analysis ofthe training data. The LAD tree classifier can generate a multi-classalternating decision tree using a LogitBoost strategy. The Multi-LayerPerception Neural Network classifier can use back-propagation toclassify instances. The Logistic Regression classifier can build linearlogistic regression models. LogitBoost with simple regression canfunction as a base learner and can be used for fitting the logisticmodels. The IBK Lazy classifier can use normalized Euclidean distance tofind the training instance closest to the given test instance, and canpredict the same class as the training instance. If multiple instanceshave the same (smallest) distance to the test instance, the first onefound can be used.

Additional information about all of the above classifiers can be foundin Richard O. Duda et al., PATTERN CLASSIFICATION (2nd. Edition), whichis herein incorporated by reference. Further information about the IBKLazy classifier can be found in Niels Landwehr et al, LOGISTIC MODELTREES (2005), which is also herein incorporated by reference.

For example, each classifier in the meta-classifier can classify vector710 as follows:

Classifier 1 (Naive Bayes Meta.) is: notknown (Confidence: 1) Classifier2 (Multi Layer Per. Meta.) is: conficker-B (Confidence: 0.985572986223)Classifier 3 (Logistic Regression Meta.) is: conficker-B (Confidence:0.374297598072) Classifier 4 (LADtree Meta.) is: conficker-B(Confidence: 0.220571723953) Classifier 5 (Lazy IB1 Meta.) is:conficker-B (Confidence: 1)

Using the classification of the vector by each classifier, if aconfidence threshold is set to be >=0.9 (note that this value can be setby the user), the meta-classifier can classify the vector (orstatistical instance) as follows:

Instance 1 Meta classification detection result: conficker-B withmajority voting value: 4 with confidence (med/std):(0.985572986223/0.345308923709). This means that a majority of four (outof five) of the classifiers found the vector to be classified asconficker-B. The median confidence score is the median of all five ofthe confidence scores, divided by the standard deviation of all five ofthe classifiers. It should be noted that, because the confidencethreshold is set to be >=0.9, this number is only meaningful if themedian confidence score is >=0.9.

FIG. 9 illustrates False Positive (FP) and True Positive (TP)classification results from the meta-classifier of FIG. 8 to one of sixdifferent malware classes: conficker-A, conficker-B, conficker-C,sinowal, bobax, and unknown: FIG. 9 indicates a FP value and a TP valuefor each type of malware. The FP rate is the False Positive detectionrates for each different class. The TP rate is the True Positivesdetection rates for each different class. The FP rate can correspond tothe percentage of vectors mistakenly classified as malicious which wereactually benign. The TP rate corresponds to the percentage of vectorsclassified as malicious that were actually malicious. The followingarticle, which is herein incorporated by reference, describes FP and TPrates in more detail: Axelsson. S., The Base-Rate Fallacy and theDifficulty of Intrusion Detection. ACM TRANS. INF. SYST. SECUR. 3, 3(August 2000), 186-205.

It should be noted that the meta-classifier can be independent from themanner in which the NXs are collected. It is only necessary to keep amapping between the internal asset that the NXs originated from. Thedetection flow is satisfied as long as the monitoring system in the realnetwork collects NXs from the same internal asset and groups them intosets of 10 using the absolute timing sequence. This is because theclassifier can be trained to detect such behavior. Thus, the trainedclassifier can utilize domain names collected in the same way in realtime.

FIG. 9 also illustrates how domain names from known malware (e.g.,sinowal, bobax, conficker) can be classified by the meta-classifierusing information learned from the training set. Domain names that donot match the training set can be classified as “notknown” or“unknownBot”. Hand verification or other methods can be used to classifythe “notknown” domain names.

It should be noted that if many NXs are classified as “unknown”, eithera DNS issue causes such characterization, or the NXs are from malwarewhere little or no information about the malware is known (e.g., a newworm). DNS issues can include a DNS outage or DNS misconfiguration. If aDNS issue is the cause of the high number of “unknown” classifications,the NXs can be classified as legitimate using for example, alexa.com, ora passive DNS feed. A passive DNS feed can be a technology whichconstructs zone replicas without cooperation from zone administrators,based on captured name server responses (see, e.g., F. Weimer, PassiveDNS Replications, http://www.enyo.de/fw/software/dnslogger/2007, whichis herein incorporated by reference). An example of a passive DNS feedis a DNSParse, which can be, for example, an implementation of thepassive DNS technology by the University of Auckland in New Zealand(see, e.g., https://dnsparse.insee.auckland.ac.nz/dns/2007, which isherein incorporated by reference).

FIG. 10 illustrates an example of how to identify similar patterns inNXs and use those patterns to train a new class (e.g., an unknown-botclass). For example, reviewing the NXs of FIG. 10, a person or computerprogram could determine malware patterns such as, but not limited to: asize of 8 (after www) with a top level domain of .com.

While various embodiments of the present invention have been describedabove, it should be understood that they have been presented by way ofexample, and not limitation. It will be apparent to persons skilled inthe relevant art(s) that various changes in form and detail can be madetherein without departing from the spirit and scope of the presentinvention. Thus, the present invention should not be limited by any ofthe above-described exemplary embodiments.

In addition, it should be understood that the figures described above,which highlight the functionality and advantages of the presentinvention, are presented for example purposes only. The architecture ofthe present invention is sufficiently flexible and configurable, suchthat it may be utilized in ways other than that shown in the figures.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope of the present inventionin any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112, paragraph 6. Claims that do not expressly include the phrase“means for” or “step for” are not to be interpreted under 35 U.S.C. 112,paragraph 6.

1. A method of analysis, comprising: collecting NX domain names from atleast one asset in at least one real network, the NX domain names beingdomain names that are not registered; using the real network NX domainnames to create testing vectors; classifying the testing vectors asbenign vectors or malicious vectors based on training vectors; andclassifying the at least one asset in the at least one real network asinfected if the NX testing vector created from the real network NXdomain names is classified as a malicious vector.
 2. The method of claim1, further comprising classifying previously unclassified malware fromthe NX domain names.
 3. The method of claim 1, wherein only DNS NXdomain name information is utilized to classify the at least one assetas infected.
 4. The method of claim 1, wherein only NX domain traffic isutilized.
 5. The method of claim 1, wherein a meta-classifier isutilized to classify the testing vectors as benign vectors or maliciousvectors.
 6. The method of claim 5, wherein the meta-classifier providesintelligence for identifying new malware.
 7. The method of claim 1,wherein the classifying of the testing vectors is done using at leastone meta-classifier, the at least one meta-classifier comprising atleast one generic classifier.
 8. The method of Clam 1, furthercomprising classifying previously classified malware from the NX domainnames.
 9. The method of claim 1, wherein the NX domain names collectedfrom the at least one honeypot and the at least one real network aregrouped into sets of 10 using absolute timing sequence information. 10.The method of claim 1, wherein the training vectors and the testingvectors are created by; computing various statistical values for atleast one set of NX domain names; and collecting the various statisticalvalues for each set of NX domain names in at least one vector.
 11. Themethod of claim 1, wherein NX domain names from honeypots are used tocreate the training vectors.
 12. A system of analysis, comprising: atleast one computer connected to at least one network; at least oneapplication connected to the at least one network, the at least oneapplication configured for: collecting NX domain names from at least oneasset in at least one real network, the NX domain names being domainnames that are not registered; using the real network NX domain names tocreate testing vectors; classifying the testing vectors as benignvectors or malicious vectors based on training vectors; and classifyingthe at least one asset in the at least one real network as infected ifthe NX testing vector created from the real network NX domain names isclassified as a malicious vector.
 13. The system of claim 12, whereinthe at least one application is further configured for classifyingpreviously unclassified malware from the NX domain names.
 14. The systemof claim 12, wherein only DNS NX domain name information is utilized toclassify the at least one asset as infected.
 15. The system of claim 12,wherein only NX domain traffic is utilized.
 16. The system of claim 12,wherein a meta-classifier is utilized to classify the testing vectors asbenign vectors or malicious vectors.
 17. The system of claim 16, whereinthe meta-classifier provides intelligence for identifying new malware.18. The system of claim 12, wherein the classifying of the testingvectors is done using at least one meta-classifier, the at least onemeta-classifier comprising at least one generic classifier.
 19. Thesystem of claim 12, wherein the at least one application is furtherconfigured for classifying previously classified malware from the NXdomain names.
 20. The system of claim 12, wherein the NX domain namescollected from the at least one honeypot and the at least one realnetwork are grouped into sets of 10 using absolute timing sequenceinformation.
 21. The system of claim 12, wherein the training vectorsand the testing vectors are created by; computing various statisticalvalues for at least one set of NX domain names; and collecting thevarious statistical values for each set of NX domain names in at leastone vector.
 22. The system of claim 12, wherein NX domain names fromhoneypots are used to create the training vectors.